Changelog: July 20, 2026 weekly update - #300
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| - **HIT Cplus transhipment mapping** — Hong Kong HIT Cplus records for inbound transhipment (`Transhipment Laden` + `Inbound On-board` → **On Ship**, + `On Dock`/`At pier` → **Grounded**) now map correctly instead of storing a blank status | ||
| - **HHLA Hamburg retries** — a transient connection drop or 5xx on HHLA's COAST API now retries once per container lookup instead of failing the whole batch's scrape log | ||
| - **Port Houston enrichments** — the Port Houston EVP tracker now surfaces **seal numbers** and picks up multi-mode holds and reefer LFD / paid-thru dates | ||
| - **Removed V1 shipment refresh endpoints** — the V1 shipment-level manual refresh actions (`refresh_containers`, `refresh_shipment`, `refresh_rail`) have been retired now that container-level refresh via the V2 API (`POST /v2/containers/refresh`) supersedes them |
There was a problem hiding this comment.
The API specification exposes container refresh as PATCH /v2/containers/{id}/refresh, not POST /v2/containers/refresh. A consumer following this entry will omit the required container ID and call an undefined method and route, causing the refresh request to fail.
Suggested change
| - **Removed V1 shipment refresh endpoints** — the V1 shipment-level manual refresh actions (`refresh_containers`, `refresh_shipment`, `refresh_rail`) have been retired now that container-level refresh via the V2 API (`POST /v2/containers/refresh`) supersedes them | |
| - **Removed V1 shipment refresh endpoints** — the V1 shipment-level manual refresh actions (`refresh_containers`, `refresh_shipment`, `refresh_rail`) have been retired now that container-level refresh via the V2 API (`PATCH /v2/containers/{id}/refresh`) supersedes them |
Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/updates/home.mdx
Line: 63
Comment:
**Replacement Refresh Route Is Invalid**
The API specification exposes container refresh as `PATCH /v2/containers/{id}/refresh`, not `POST /v2/containers/refresh`. A consumer following this entry will omit the required container ID and call an undefined method and route, causing the refresh request to fail.
```suggestion
- **Removed V1 shipment refresh endpoints** — the V1 shipment-level manual refresh actions (`refresh_containers`, `refresh_shipment`, `refresh_rail`) have been retired now that container-level refresh via the V2 API (`PATCH /v2/containers/{id}/refresh`) supersedes them
```
How can I resolve this? If you propose a fix, please make it concise.
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the July 20, 2026 changelog entry covering PRs merged since the last entry.
Changes
Greptile Summary
This PR adds the July 20, 2026 weekly changelog entry. The main changes are:
Confidence Score: 4/5
The documented container-refresh route needs correction before merging.
docs/updates/home.mdx
Important Files Changed
Prompt To Fix All With AI
Reviews (1): Last reviewed commit: "docs: add July 20, 2026 changelog entry" | Re-trigger Greptile